Extra examples of migrating keyCode modifiers #1125
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original motivation here is trying to explain how to handle punctuation characters. The RFC doesn't seem to acknowledge this problem.
event.key
exposes printable keys as single-character strings, equal to the printable character. There is no 'kebab-case named' equivalent, you just have to write the character literally in the attribute. In many cases that isn't possible as the character isn't syntactically valid. I'm not aware of any workaround for this, aside from not using the modifier.I've also changed the existing example. The
delete
key has special internal handling, so I don't think it's the most suitable choice for an example.page-down
illustrates the use of kebab-case. Theq
example illustrates how the conversion to kebab-case results in letters being matched case-insensitively.